Notes/Domino Fix List
 |  |
| SPR # MHAC68CPNX | Fixed in 6.5.5 release |  |
Product Area: Server Technical Area: Clusters Platform: Cross Platform
Lotus Customer Support APAR: LO06043
SPR# MHAC68CPNX - Failover to a secondary cluster server broke framesets in the mail file. Error "Invalid URL Syntax" was displayed and the frameset never opened. This problem has been fixed in 6.5.5.
Technote Number: 1193745
Problem:
This issue has been reported to Quality Engineering as SPR# MHAC68CPNX and has
been fixed in 6.5.5 and 7.0.
Excerpt from the Lotus Notes and Domino Release 6.5.5 MR and 7.0 fix lists
(available at http://www.ibm.com/developerworks/lotus):
Clusters
SPR# MHAC68CPNX - Failover to a secondary cluster server broke framesets in the
mail file. Error "Invalid URL Syntax" was displayed and the frameset never
opened. This problem has been fixed in 6.5.5 and 7.0.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Workaround for previous releases:
Open the cache.ndk local (File -> Database -> Open, and in the File name box,
type "cache.ndk").
Go the (byurl) view, select all the documents and delete them.
Open the bookmark.nsf local:
a. In the Workspace, highlight the bookmark icon.
b. Hold down the SHIFT and CTRL keys, and from the menu, select View -> Go to
-> hidden view (byurl).
c. In the same view, select all document and delete them.
Note: Following the steps above could result in losing settings for views
(column order and column width). However, deleting the cache or removing
documents from bookmarks can have the same effect.
Supporting Information:
This issue appears to occur because of cache entries which are incorrectly
recorded into bookmark.nsf. When the client attempts to refer to these entries
later, the errors occur. If the documents in the ((byurl)) view of the
bookmark.nsf database are examined, you will find that the NoteID of one or
more of the entries does not correspond to a design element within your mail
file*. This invalid entry results in the unexpected behavior. The relative
NoteID may actually correspond to a document in the cache.dsk which itself
refers to a design element in the mail file.
*Note: In some cases, the NoteID may refer to an existing design element in the
mail file.
The following steps demonstrate the issue above:
1. Open the mail file.
2. Open bookmark.nsf database using CTRL-SHIFT View -> Goto -> ((byurl)).
3. Delete all entries in the view.
4. Resize the Inbox of the mail file using the option View -> Customize This
View.
5. Close the mail file.
6. Refresh the opened view in the bookmark.nsf.
7. Note that the view contains three entries:
Entry with UNID which corresponds to the ($inbox) folder
Entry with NoteID 94E which corresponds to a form called (TraceReport)
Entry with a NoteID which corresponds to the NoteID of the ($inbox) folder
The second entry is the problem entry. Given the activity in the example, a
reference to a form is not be expected. In this case, the NoteID reference just
happened to correspond to a design element within the mail file. During
customization, the $inbox folder was updated. In the cache.ndk, the location of
a note with NoteID94E corresponds with the $inbox folder that was updated
during customization. More >
Last Modified on 12/08/2013
Go back
|